Autogenerated HTML docs for v1.7.9-48-g85da4d
diff --git a/RelNotes/1.7.10.txt b/RelNotes/1.7.10.txt new file mode 100644 index 0000000..cc22281 --- /dev/null +++ b/RelNotes/1.7.10.txt
@@ -0,0 +1,69 @@ +Git v1.7.10 Release Notes +========================= + +Updates since v1.7.9 +-------------------- + +UI, Workflows & Features + + * Improved handling of views, labels and branches in git-p4 (in contrib). + + * "git am" learned to pass "-b" option to underlying "git mailinfo", so + that bracketed string other than "PATCH" at the beginning can be kept. + + * "git clone" learned "--single-branch" option to limit cloning to a + single branch (surprise!). + + * When showing a patch while ignoring whitespace changes, the context + lines are taken from the postimage, in order to make it easier to + view the output. + +Performance + + * During "git upload-pack" in respose to "git fetch", unnecessary calls + to parse_object() have been eliminated, to help performance in + repositories with excessive number of refs. + +Internal Implementation + + * Recursive call chains in "git index-pack" to deal with long delta + chains have been flattened, to reduce the stack footprint. + + * Use of add_extra_ref() API is slowly getting removed, to make it + possible to cleanly restructure the overall refs API. + + * The test suite supports the new "test_pause" helper function. + +Also contains minor documentation updates and code clean-ups. + + +Fixes since v1.7.9 +------------------ + +Unless otherwise noted, all the fixes since v1.7.9 in the maintenance +releases are contained in this release (see release notes to them for +details). + + * When "git push" fails to update any refs, the client side did not + report an error correctly to the end user. + (merge 5238cbf sp/smart-http-failure-to-push later to maint). + + * "git push -q" was not sufficiently quiet. + (merge d336572 cb/push-quiet later to maint). + + * "git log --first-parent $pathspec" did not stay on the first parent + chain and veered into side branch from which the whole change to the + specified paths came. + (merge 36ed191 jc/maint-log-first-parent-pathspec later to maint). + + * Subprocesses spawned from various git programs were often left running + to completion even when the top-level process was killed. + (merge 10c6cdd cb/maint-kill-subprocess-upon-signal later to maint). + +--- +exec >/var/tmp/1 +O=v1.7.9 +echo O=$(git describe) +git log --first-parent --oneline ^maint $O.. +echo +git shortlog --no-merges ^maint $O..
diff --git a/git-am.html b/git-am.html index 1e22159..9f4d8f6 100644 --- a/git-am.html +++ b/git-am.html
@@ -637,6 +637,14 @@ </p> </dd> <dt class="hdlist1"> +--keep-non-patch +</dt> +<dd> +<p> + Pass <tt>-b</tt> flag to <em>git mailinfo</em> (see <a href="git-mailinfo.html">git-mailinfo(1)</a>). +</p> +</dd> +<dt class="hdlist1"> --keep-cr </dt> <dt class="hdlist1"> @@ -915,7 +923,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2011-11-15 13:45:02 PDT +Last updated 2012-01-29 14:19:30 PDT </div> </div> </body>
diff --git a/git-am.txt b/git-am.txt index 887466d..ee6cca2 100644 --- a/git-am.txt +++ b/git-am.txt
@@ -40,6 +40,9 @@ --keep:: Pass `-k` flag to 'git mailinfo' (see linkgit:git-mailinfo[1]). +--keep-non-patch:: + Pass `-b` flag to 'git mailinfo' (see linkgit:git-mailinfo[1]). + --keep-cr:: --no-keep-cr:: With `--keep-cr`, call 'git mailsplit' (see linkgit:git-mailsplit[1])
diff --git a/git-clone.html b/git-clone.html index 66e51d6..02feb88 100644 --- a/git-clone.html +++ b/git-clone.html
@@ -587,7 +587,8 @@ [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror] [-o <name>] [-b <name>] [-u <upload-pack>] [--reference <repository>] [--separate-git-dir <git dir>] - [--depth <depth>] [--recursive|--recurse-submodules] [--] <repository> + [--depth <depth>] [--[no-]single-branch] + [--recursive|--recurse-submodules] [--] <repository> [<directory>]</div> <div class="verseblock-attribution"> </div></div> @@ -847,6 +848,19 @@ </p> </dd> <dt class="hdlist1"> +--single-branch +</dt> +<dd> +<p> + Clone only the history leading to the tip of a single branch, + either specified by the <tt>--branch</tt> option or the primary + branch remote’s <tt>HEAD</tt> points at. When creating a shallow + clone with the <tt>--depth</tt> option, this is the default, unless + <tt>--no-single-branch</tt> is given to fetch the histories near the + tips of all branches. +</p> +</dd> +<dt class="hdlist1"> --recursive </dt> <dt class="hdlist1"> @@ -1090,7 +1104,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2011-11-15 13:45:02 PDT +Last updated 2012-01-29 14:19:30 PDT </div> </div> </body>
diff --git a/git-clone.txt b/git-clone.txt index 4b8b26b..0931a3e 100644 --- a/git-clone.txt +++ b/git-clone.txt
@@ -13,7 +13,8 @@ [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror] [-o <name>] [-b <name>] [-u <upload-pack>] [--reference <repository>] [--separate-git-dir <git dir>] - [--depth <depth>] [--recursive|--recurse-submodules] [--] <repository> + [--depth <depth>] [--[no-]single-branch] + [--recursive|--recurse-submodules] [--] <repository> [<directory>] DESCRIPTION @@ -179,6 +180,14 @@ with a long history, and would want to send in fixes as patches. +--single-branch:: + Clone only the history leading to the tip of a single branch, + either specified by the `--branch` option or the primary + branch remote's `HEAD` points at. When creating a shallow + clone with the `--depth` option, this is the default, unless + `--no-single-branch` is given to fetch the histories near the + tips of all branches. + --recursive:: --recurse-submodules:: After the clone is created, initialize all submodules within,
diff --git a/git-p4.html b/git-p4.html index 5a7f5ed..316b9a4 100644 --- a/git-p4.html +++ b/git-p4.html
@@ -1012,6 +1012,10 @@ around whitespace. Of the possible wildcards, git-p4 only handles <em>…</em>, and only when it is at the end of the path. Git-p4 will complain if it encounters an unhandled wildcard.</p></div> +<div class="paragraph"><p>Bugs in the implementation of overlap mappings exist. If multiple depot +paths map through overlays to the same location in the repository, +git-p4 can choose the wrong one. This is hard to solve without +dedicating a client spec just for git-p4.</p></div> <div class="paragraph"><p>The name of the client can be given to git-p4 in multiple ways. The variable <em>git-p4.client</em> takes precedence if it exists. Otherwise, normal p4 mechanisms of determining the client are used: environment @@ -1303,7 +1307,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2012-01-06 13:52:20 PDT +Last updated 2012-01-29 14:19:30 PDT </div> </div> </body>
diff --git a/git-p4.txt b/git-p4.txt index 78938b2..8b92cc0 100644 --- a/git-p4.txt +++ b/git-p4.txt
@@ -314,6 +314,11 @@ '...', and only when it is at the end of the path. Git-p4 will complain if it encounters an unhandled wildcard. +Bugs in the implementation of overlap mappings exist. If multiple depot +paths map through overlays to the same location in the repository, +git-p4 can choose the wrong one. This is hard to solve without +dedicating a client spec just for git-p4. + The name of the client can be given to git-p4 in multiple ways. The variable 'git-p4.client' takes precedence if it exists. Otherwise, normal p4 mechanisms of determining the client are used: environment
